QVAC-18184 chore[skiplog]: backmerge release sdk 0.9.2 by simon-iribarren · Pull Request #1857 · tetherto/qvac

simon-iribarren · 2026-05-01T10:43:33Z

Note: be concise and prefer bullet points.

🎯 What problem does this PR solve?

@qvac/sdk@0.9.2 was published to npm earlier today (latest dist-tag, 2026-05-01 10:09 UTC) from release-sdk-0.9.2, but main has no record of the 0.9.2 release.
Every prior SDK release closes the loop with a backmerge of the release artifacts back into main (precedent: chore[notask]: backmerge release sdk 0.9.1 #1726 for 0.9.1, QVAC-16776 chore[skiplog]: backmerge release-sdk-0.9.0 — changelog, NOTICE, model registry, and tooling fixes #1645 for 0.9.0, chore[notask|skiplog]: backmerge release sdk v0.8.3 #1552 for 0.8.3, doc[notask]: backmerge release-sdk-0.8.2 into main #1533 for 0.8.2, QVAC-16495 chore[skiplog]: backmerge sdk v0.8.1 release, changelog & NOTICE #1301 for 0.8.1). Without this, the next changelog generation on main has a 0.9.1 → 0.10.0 hole.

📝 How does it solve it?

Hand-crafted backmerge of the changelog artifacts only (not a git merge — see "How was it tested?"):
- packages/sdk/changelog/0.9.2/CHANGELOG.md: new file (copied verbatim from release-sdk-0.9.2)
- packages/sdk/changelog/0.9.2/CHANGELOG_LLM.md: new file (copied verbatim from release-sdk-0.9.2)
- packages/sdk/CHANGELOG.md: prepend the ## [0.9.2] block above the existing ## [0.9.1] block
packages/sdk/package.json version bump intentionally NOT included. PR QVAC-16777 feat[skiplog]: improve sdk-changelog tooling and add 0.10.0 release notes #1865 (the 0.10.0 release targeting main) bumps the same version line 0.9.1 → 0.10.0. To avoid a guaranteed conflict on that single line, this PR leaves the version field alone and lets QVAC-16777 feat[skiplog]: improve sdk-changelog tooling and add 0.10.0 release notes #1865 own the bump. main's package.json will briefly say 0.9.1 while CHANGELOG.md lists 0.9.2 as the latest shipped version, but that's transient — QVAC-16777 feat[skiplog]: improve sdk-changelog tooling and add 0.10.0 release notes #1865 overwrites it to 0.10.0.
Net diff vs. the precedent chore[notask]: backmerge release sdk 0.9.1 #1726 shape: 3 files instead of 4 (no package.json).

🧪 How was it tested?

Why hand-crafted, not git merge: the source-level hotfix (z.xor → z.union, zod floor bump from fix[notask]: replace z.xor with z.union, bump zod floor to ^4.3.0 #1790) is already on main, so no source changes need to come back. A blind merge of release-sdk-0.9.2 into main would regress packages/sdk/package.json dependencies because main has progressed past 0.9.1 on several internal packages:

dep	release-sdk-0.9.2	main
`@qvac/diffusion-cpp`	`^0.1.3`	`^0.3.0`
`@qvac/llm-llamacpp`	`^0.14.4`	`^0.17.1`
`@qvac/translation-nmtcpp`	`^0.6.10`	`^2.0.1`
`@qvac/tts-onnx`	`^0.8.2`	`^0.8.4`
`@qvac/embed-llamacpp`	`^0.13.4`	`^0.14.0`
`@qvac/cli`	`^0.2.3`	`^0.2.4`
`react-native-bare-kit`	`^0.11.5`	`0.12.3`
`bare-fs` (peer)	`^4.5.2`	`^5.x`
`bare-link` (peer)	`^2.1.10`	`^3.2.1`

Diff verified to touch only the 0.9.2/ changelog folder and the prepended ## [0.9.2] aggregated entry. package.json matches upstream/main exactly (git diff upstream/main -- packages/sdk/package.json returns empty).
Awaiting CI green.

Brings the 0.9.2 release artifacts back into main now that @qvac/sdk@0.9.2 has been published to npm (`latest` dist-tag, 2026-05-01 10:09 UTC). - Bump packages/sdk/package.json: 0.9.1 -> 0.9.2 - Add packages/sdk/changelog/0.9.2/CHANGELOG.md and CHANGELOG_LLM.md - Prepend 0.9.2 entry to aggregated packages/sdk/CHANGELOG.md Hotfix content (z.xor -> z.union, zod floor bump) is the cherry-pick of tetherto#1790 that already landed on main, so no source changes here. Dependencies in package.json are intentionally NOT brought over from the release branch — main has progressed past 0.9.1 on several internal packages (e.g. @qvac/llm-llamacpp 0.14.4 -> 0.17.1, @qvac/translation-nmtcpp 0.6.10 -> 2.0.1, react-native-bare-kit 0.11.5 -> 0.12.3) and a blind merge would regress them. Only the version field is changed, matching the 0.9.1 backmerge precedent (tetherto#1726).

…d conflict with 0.10.0 PR PR tetherto#1865 (the 0.10.0 release) is open against main and bumps packages/sdk/package.json version 0.9.1 -> 0.10.0. This backmerge was bumping the same line 0.9.1 -> 0.9.2, so whichever lands second hits a conflict on that single line. Since main is moving to 0.10.0 directly (the 0.9.2 hotfix is a separate release line), drop the package.json change from this backmerge and let tetherto#1865 own the version bump. Main's package.json will briefly say 0.9.1 while CHANGELOG.md lists 0.9.2 as the latest shipped version, but that's transient — tetherto#1865 overwrites it to 0.10.0 anyway. Keep the changelog artifacts (changelog/0.9.2/ folder + the prepended ## [0.9.2] entry in aggregated CHANGELOG.md) so main retains a record of the 0.9.2 release in its history.

…-0.9.2 # Conflicts: # packages/sdk/CHANGELOG.md

NamelsKing · 2026-05-03T11:58:26Z

/review

github-actions · 2026-05-03T11:58:54Z

Tier-based Approval Status

**PR Tier:** TIER1

**Current Status:** ✅ APPROVED

**Requirements:**
- 1 Team Member approval ✅ (1/1)
- 1 Team Lead OR Management approval ✅ (1/1)



---
*This comment is automatically updated when reviews change.*

lauripiisang · 2026-05-04T08:18:13Z

/review

…angelog (#1867) Brings the @qvac/cli@0.3.0 release artifacts back onto main per gitflow.md "Keep main aligned". Same shape as #1766 (the 0.2.4 backmerge precedent). - packages/cli/package.json: version 0.2.4 -> 0.3.0 - packages/cli/changelog/0.3.0/CHANGELOG.md: new - packages/cli/changelog/0.3.0/api.md: new - packages/cli/CHANGELOG.md: prepend ## [0.3.0] entry NOTE: Opened as DRAFT because the companion release PR #1836 is also still draft and 5 of its CI checks are failing. @qvac/cli@0.3.0 has not yet been published to npm (latest is 0.2.4). Mark this PR ready for review only after #1836 merges into release-cli-0.3.0 and the GPR/npm publish completes. The source-level changes (@qvac/sdk devDep ^0.10.0 + sdk.ts MIN_SDK_VERSION='0.10.0') are already on main from PR #1810 — only the release metadata needs to come back. CLI's package.json on main has no dependency drift versus release-cli-0.3.0, so unlike the SDK 0.9.2 backmerge (#1857) the package.json version bump can be safely included here. There's also no competing CLI release PR in flight on main. Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>

* QVAC-18184 chore[notask|skiplog]: backmerge release sdk 0.9.2 Brings the 0.9.2 release artifacts back into main now that @qvac/sdk@0.9.2 has been published to npm (`latest` dist-tag, 2026-05-01 10:09 UTC). - Bump packages/sdk/package.json: 0.9.1 -> 0.9.2 - Add packages/sdk/changelog/0.9.2/CHANGELOG.md and CHANGELOG_LLM.md - Prepend 0.9.2 entry to aggregated packages/sdk/CHANGELOG.md Hotfix content (z.xor -> z.union, zod floor bump) is the cherry-pick of #1790 that already landed on main, so no source changes here. Dependencies in package.json are intentionally NOT brought over from the release branch — main has progressed past 0.9.1 on several internal packages (e.g. @qvac/llm-llamacpp 0.14.4 -> 0.17.1, @qvac/translation-nmtcpp 0.6.10 -> 2.0.1, react-native-bare-kit 0.11.5 -> 0.12.3) and a blind merge would regress them. Only the version field is changed, matching the 0.9.1 backmerge precedent (#1726). * chore[skiplog]: drop package.json version bump from backmerge to avoid conflict with 0.10.0 PR PR #1865 (the 0.10.0 release) is open against main and bumps packages/sdk/package.json version 0.9.1 -> 0.10.0. This backmerge was bumping the same line 0.9.1 -> 0.9.2, so whichever lands second hits a conflict on that single line. Since main is moving to 0.10.0 directly (the 0.9.2 hotfix is a separate release line), drop the package.json change from this backmerge and let #1865 own the version bump. Main's package.json will briefly say 0.9.1 while CHANGELOG.md lists 0.9.2 as the latest shipped version, but that's transient — #1865 overwrites it to 0.10.0 anyway. Keep the changelog artifacts (changelog/0.9.2/ folder + the prepended ## [0.9.2] entry in aggregated CHANGELOG.md) so main retains a record of the 0.9.2 release in its history. --------- Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>

…angelog (#1867) Brings the @qvac/cli@0.3.0 release artifacts back onto main per gitflow.md "Keep main aligned". Same shape as #1766 (the 0.2.4 backmerge precedent). - packages/cli/package.json: version 0.2.4 -> 0.3.0 - packages/cli/changelog/0.3.0/CHANGELOG.md: new - packages/cli/changelog/0.3.0/api.md: new - packages/cli/CHANGELOG.md: prepend ## [0.3.0] entry NOTE: Opened as DRAFT because the companion release PR #1836 is also still draft and 5 of its CI checks are failing. @qvac/cli@0.3.0 has not yet been published to npm (latest is 0.2.4). Mark this PR ready for review only after #1836 merges into release-cli-0.3.0 and the GPR/npm publish completes. The source-level changes (@qvac/sdk devDep ^0.10.0 + sdk.ts MIN_SDK_VERSION='0.10.0') are already on main from PR #1810 — only the release metadata needs to come back. CLI's package.json on main has no dependency drift versus release-cli-0.3.0, so unlike the SDK 0.9.2 backmerge (#1857) the package.json version bump can be safely included here. There's also no competing CLI release PR in flight on main. Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>

* QVAC-18184 chore[notask|skiplog]: backmerge release sdk 0.9.2 Brings the 0.9.2 release artifacts back into main now that @qvac/sdk@0.9.2 has been published to npm (`latest` dist-tag, 2026-05-01 10:09 UTC). - Bump packages/sdk/package.json: 0.9.1 -> 0.9.2 - Add packages/sdk/changelog/0.9.2/CHANGELOG.md and CHANGELOG_LLM.md - Prepend 0.9.2 entry to aggregated packages/sdk/CHANGELOG.md Hotfix content (z.xor -> z.union, zod floor bump) is the cherry-pick of #1790 that already landed on main, so no source changes here. Dependencies in package.json are intentionally NOT brought over from the release branch — main has progressed past 0.9.1 on several internal packages (e.g. @qvac/llm-llamacpp 0.14.4 -> 0.17.1, @qvac/translation-nmtcpp 0.6.10 -> 2.0.1, react-native-bare-kit 0.11.5 -> 0.12.3) and a blind merge would regress them. Only the version field is changed, matching the 0.9.1 backmerge precedent (#1726). * chore[skiplog]: drop package.json version bump from backmerge to avoid conflict with 0.10.0 PR PR #1865 (the 0.10.0 release) is open against main and bumps packages/sdk/package.json version 0.9.1 -> 0.10.0. This backmerge was bumping the same line 0.9.1 -> 0.9.2, so whichever lands second hits a conflict on that single line. Since main is moving to 0.10.0 directly (the 0.9.2 hotfix is a separate release line), drop the package.json change from this backmerge and let #1865 own the version bump. Main's package.json will briefly say 0.9.1 while CHANGELOG.md lists 0.9.2 as the latest shipped version, but that's transient — #1865 overwrites it to 0.10.0 anyway. Keep the changelog artifacts (changelog/0.9.2/ folder + the prepended ## [0.9.2] entry in aggregated CHANGELOG.md) so main retains a record of the 0.9.2 release in its history. --------- Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>

…angelog (#1867) Brings the @qvac/cli@0.3.0 release artifacts back onto main per gitflow.md "Keep main aligned". Same shape as #1766 (the 0.2.4 backmerge precedent). - packages/cli/package.json: version 0.2.4 -> 0.3.0 - packages/cli/changelog/0.3.0/CHANGELOG.md: new - packages/cli/changelog/0.3.0/api.md: new - packages/cli/CHANGELOG.md: prepend ## [0.3.0] entry NOTE: Opened as DRAFT because the companion release PR #1836 is also still draft and 5 of its CI checks are failing. @qvac/cli@0.3.0 has not yet been published to npm (latest is 0.2.4). Mark this PR ready for review only after #1836 merges into release-cli-0.3.0 and the GPR/npm publish completes. The source-level changes (@qvac/sdk devDep ^0.10.0 + sdk.ts MIN_SDK_VERSION='0.10.0') are already on main from PR #1810 — only the release metadata needs to come back. CLI's package.json on main has no dependency drift versus release-cli-0.3.0, so unlike the SDK 0.9.2 backmerge (#1857) the package.json version bump can be safely included here. There's also no competing CLI release PR in flight on main. Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>

simon-iribarren requested a review from a team as a code owner May 1, 2026 10:43

simon-iribarren added verify tier1 labels May 1, 2026

simon-iribarren requested a review from a team as a code owner May 1, 2026 10:43

simon-iribarren had a problem deploying to release May 1, 2026 10:43 — with GitHub Actions Failure

simon-iribarren changed the title ~~QVAC-18184 chore[notask|skiplog]: backmerge release sdk 0.9.2~~ QVAC-18184 chore[skiplog]: backmerge release sdk 0.9.2 May 1, 2026

simon-iribarren had a problem deploying to release May 1, 2026 10:53 — with GitHub Actions Failure

simon-iribarren mentioned this pull request May 1, 2026

infra[skiplog]: document release & backmerge PR conventions in sdk-pr-create skill #1858

Closed

simon-iribarren had a problem deploying to release May 1, 2026 10:59 — with GitHub Actions Failure

Merge branch 'main' into chore/backmerge-sdk-0.9.2

2691519

simon-iribarren had a problem deploying to release May 1, 2026 11:47 — with GitHub Actions Failure

simon-iribarren had a problem deploying to release May 1, 2026 11:52 — with GitHub Actions Failure

opaninakuffo previously approved these changes May 1, 2026

View reviewed changes

lauripiisang previously approved these changes May 1, 2026

View reviewed changes

Merge branch 'main' into chore/backmerge-sdk-0.9.2

3acf7e7

simon-iribarren had a problem deploying to release May 1, 2026 14:11 — with GitHub Actions Failure

simon-iribarren dismissed stale reviews from lauripiisang and opaninakuffo via e3c8605 May 1, 2026 14:16

simon-iribarren had a problem deploying to release May 1, 2026 14:16 — with GitHub Actions Failure

simon-iribarren had a problem deploying to release May 1, 2026 14:17 — with GitHub Actions Failure

simon-iribarren mentioned this pull request May 1, 2026

chore[skiplog|notask]: backmerge release-cli-0.3.0 — version bump, changelog #1867

Merged

opaninakuffo previously approved these changes May 1, 2026

View reviewed changes

NamelsKing previously approved these changes May 1, 2026

View reviewed changes

Merge remote-tracking branch 'upstream/main' into chore/backmerge-sdk…

aa839ec

…-0.9.2 # Conflicts: # packages/sdk/CHANGELOG.md

simon-iribarren dismissed stale reviews from NamelsKing and opaninakuffo via aa839ec May 2, 2026 09:33

simon-iribarren had a problem deploying to release May 2, 2026 09:33 — with GitHub Actions Failure

Merge branch 'main' into chore/backmerge-sdk-0.9.2

67ab6ee

NamelsKing had a problem deploying to release May 3, 2026 11:58 — with GitHub Actions Failure

NamelsKing approved these changes May 3, 2026

View reviewed changes

lauripiisang approved these changes May 4, 2026

View reviewed changes

Victor-Rodzko approved these changes May 4, 2026

View reviewed changes

NamelsKing approved these changes May 4, 2026

View reviewed changes

NamelsKing merged commit 871eea2 into tetherto:main May 4, 2026
16 of 19 checks passed

NamelsKing had a problem deploying to release May 4, 2026 08:19 — with GitHub Actions Failure

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

QVAC-18184 chore[skiplog]: backmerge release sdk 0.9.2#1857

QVAC-18184 chore[skiplog]: backmerge release sdk 0.9.2#1857
NamelsKing merged 6 commits into
tetherto:mainfrom
simon-iribarren:chore/backmerge-sdk-0.9.2

simon-iribarren commented May 1, 2026 •

edited

Loading

Uh oh!

NamelsKing commented May 3, 2026

Uh oh!

github-actions Bot commented May 3, 2026 •

edited

Loading

Uh oh!

lauripiisang commented May 4, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

Conversation

simon-iribarren commented May 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🎯 What problem does this PR solve?

📝 How does it solve it?

🧪 How was it tested?

Uh oh!

NamelsKing commented May 3, 2026

Uh oh!

github-actions Bot commented May 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Tier-based Approval Status

Uh oh!

lauripiisang commented May 4, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

simon-iribarren commented May 1, 2026 •

edited

Loading

github-actions Bot commented May 3, 2026 •

edited

Loading